Self-Checkout (SCO) in LS Central — Two Approaches

LS Central supports self-checkout in two distinct ways:

LS CentralPOS with a Self Checkout layout

The standard LS CentralPOS can be configured to run directly as a self-checkout (SCO) user interface on a device serving as a self-service terminal, without requiring any additional connectors or external services.
With the release of LS Central version 28.0, enhancements to POS controls have improved flexibility and usability, making it a more practical option for self-checkout scenarios. This makes it a strong option if you want greater flexibility in your choice of hardware, while also maintaining full control over the look and feel of the POS interface, and do not require specialized SCO hardware (such as integrated security scales or other device-specific components).
As this approach does not include hardware-integrated security features (for example, from SCO-specific hardware vendors), loss prevention should be considered as part of the overall store setup and operational processes.
To learn how to configure this setup, see: Set UpLS CentralPOS with a Self Checkout layout

The Self-Checkout Connector (SCO Module)

The SCO Connector is a bridge between LS Central and self-checkout devices from different hardware manufacturers. It enables seamless communication through web services to support core checkout operations such as item scanning, transaction processing, tender handling, and device workflows. It is not used when the LS Central POS itself runs as the user interface on a self-service checkout terminal.

Supported Hardware

The Self-Checkout Connector supports the following device types:

Diebold Nixdorf self-checkout devices
NCR self-checkout devices (in final testing)
Custom implementations using a plugin-based architecture.

Architecture

The SCO Connector acts as the central integration layer. Its responsibilities include exposing a unified interface to self-checkout devices, translating device requests into LS Central Web Service calls, handling authentication with Business Central, applying business rules and Feature Flags, and routing payment and printing requests to Hardware Station.

A typical transaction flow works like this: A customer performs an action on the SCO device (e.g., scanning an item) → the device sends a request to the SCO Connector → SCO validates and applies Feature Flags → SCO calls the appropriate LS Central Web Service → if payment or printing is required, SCO contacts Hardware Station → the response is returned to the device.

Deployment Models

SCO can be installed in two ways:

1–1 installation — a single SCO instance installed directly on a self-checkout device
1–N installation — a single SCO instance on a central server communicates with multiple SCO devices

For example, it can run centrally on a store server connecting to multiple SCO devices while communicating with LS Central in the cloud. Alternatively, it can run directly on an SCO device, where all communication happens locally on the terminal.

On-Premises vs. SaaS

SCO supports both LS Central deployment types:

• On-premises — uses NavUserPass authentication and requires a Web Service Access Key.

• SaaS — uses Server-to-Server (S2S) OAuth authentication with Azure AD application registration.

Core Functional Capabilities

The SCO Connector enables self-checkout devices to:

Start and manage transactions
Add, modify, or void items and orders
Retrieve item, device, and terminal configuration
Handle staff logon and card entry
Print previous transactions
Apply business rules and restrictions using Feature Flags.

Extensibility — Feature Flags

Feature flags are configuration switches used to control behavior without code changes. They can be set at the level of the SCO Connector, Device Type, or Item Profile, depending on the scope of the feature. See Feature Flags for SCO Connector for detailed information.

Version Compatibility

The Self-Checkout Connector must always match the LS Central major version it connects to. For example, LS Central version 27 requires SCO version 27.

Summary for the two approaches for SCO

Aspect	Detail
Native SCO POS	LS Central POS runs directly on SCO terminal
SCO Connector	Middleware for Diebold Nixdorf, NCR, custom hardware
Deployment	1–1 (on device) or 1–N (central server)
Cloud/On-prem	Both supported
Payments & Printing	Via Hardware Station
Extensibility	Feature Flags per connector, device type, or item

The SCO Connector approach gives LS Central broad hardware compatibility without requiring deep per-vendor development, making it a strong story for retailers who already have SCO hardware in place or want flexibility in vendor selection.